Complete the Export

To validate and run an export job, ensure the procedures were completed in Create Export Sets:

1. Get Started:

   1. If a saved public search representing the documents to be produced does not exist, create and save the needed search as explained in ADD Review Enter Case Help.

   2. If Production Shield has not been set for the desired search and you want security applied to this export job, right click the desired search and choose Set Production Shield. See About the Production Shield for additional information.

   3. If the export set is saved/not open, click to access the Export setup page. Select the export set.

2. In the Export Tools section of the page, click .

3. In the Select Documents dialog box, select the needed saved search and optionally select fields to sort by and their sort order. Click OK.

4. Click and evaluate the Validation Report. A typical report is shown in the following figure; different entries will exist depending on your export selections.

5. If the report identifies conflicts, resolve the conflicts. Possible issues and override details are explained in the following table. In the table, Override indicators are as follows:

Y = Can be overridden

S = Can sometimes be overridden (depending on circumstances)

N = Cannot be overridden

Export/Production Troubleshooting

Conflict	Override?	Description
Missing natives	S	One or more native files in the production set do not exist in the location defined for the case. Can be overridden if you are exporting both images and native files, in which case missing native files will simply be skipped. Cannot be overridden if you are exporting only native files. To correct this conflict, take such actions as placing needed native files in the correct location or changing the export set to exclude those documents.
Missing images	No	No image is associated with one or more documents in the export set (no image path is defined). Correct this conflict by actions such as adding a custom placeholder for records lacking an image path, or performing a global replace for the image path. For details, see: "Select Output Locations" step 3 "Globally Replacing Image Paths" NOTE: Other image problems are not considered to be missing images. For example, an incorrect file path, an image missing in the specified location, server problems, etc. They are indicated in the production export by an “Error Processing Image” placeholder. Make corrections to these types of problems on a case by case basis, depending on the type of problem.
Missing text	Yes	One or more text files in the export set do not exist in the location specified for the files. If this problem is overridden, a “Missing Text” placeholder page will be included for each missing text file. Alternatively, correct this conflict by such actions as placing needed text files in the defined location or changing the production set to exclude those documents.
Missing Enddocs	No	Indicates the number of fields that are vacant. Make corrections by locating the saved search. Click the Advanced Search tab and under Field Search, choose ENDDOC from the drop-down list. Populate the field(s) and save the changes.
Missing Priority Documents	No	One or images are missing when produced. In Eclipse, enterprise image the missing document or documents.
Shield conflicts	Yes	Export documents are checked for all defined rules. Before overriding this issue, review the rules and documents in the document set to make sure overriding is the correct action.
Valid output path	No	The defined Output Location cannot be verified. Correct the location. Make sure the following conditions are met: The location is in UNCThe Universal Naming Convention (UNC) is a way to identify a shared file in a computer without having to specify (or know) the storage device it is on. format (such as \\server001\productions\ smith-jones\). The destination folder exists. The path was not used for a previous export. Ipro ADDAutomated Digital Discovery has access to the location (for example, it is in the same or a trusted domain). A volume with same name as the one defined for this production set does not already exist in the output location.
Valid native naming field	No	Occurs if naming native files by a field and the field contains no data (or only spaces or an empty string) for some documents. Either change the way native files are named or edit the empty fields so that they contain the needed data.
Broken family	Yes	Include Family is part of the saved search used to specify documents for the export set, and not all family documents can be located. Before overriding this issue, review documents in the document set to make sure overriding is the correct action.
Bates Number conflict	No	This conflict will occur a) only if DocumentIn eCapture, refers to an electronic file (letter, spreadsheet, slideshow, etc.) that can be discovered; or discovered and processed. Numbering is Use image priority and b) only if documents with duplicate numbers have been selected from the various document sets (original image and/or production export jobs chosen for this export). Resolve duplicate numbers by such actions as changing the order of document sets selected for numbering or choosing a different type of numbering.

6. Continue as follows:

   • If conflicts were found, make needed corrections and/or override the conflicts as required. then go to step 7.

   • If no conflicts were found, go to step 8.

7. After resolving or overriding conflicts, click to re-check the export set.

8. After all conflicts are resolved and/or overridden, click to start the export (The button is available only when all conflicts have been addressed.)

9. Optional: Click (located in the bottom right of the Status area) to refresh the data in the Status area.

10. Observe Status below Summary in the right pane. Status will change as process steps complete, and may include the terms listed in the following table.

Export Status Details

Status	Description
Not Started	The export process has not yet begun.
Staging	The export data is being placed in the staging database.
Staging Complete	All export data is in the staging database.
Pending	The export job has been placed in a queue.
In Progress	The export data is being processed.
Paused	The export job has been placed on hold.
Deleting	The export job has been canceled and ADD is retrieving data about the job, such as errors and information about the status of the job at the point of cancellation.
Deleted	Cancellation has been completed.
Complete	The production job has finished; production data may be transferring from the staging database back to ADD or the data transfer may have finished.

11. When the export job is complete, export files are ready for use.

12. If errors exist, click the Total Errors number (a link). An Export Errors dialog opens and shows information about document errors, page errors, and load file errors. Details can be exported to a .CSVA comma-separated values (CSV) file used to store tabular data. file if needed.